Issue #15514 - Avoid duplicate lifecycle failure logging - #15521
Open
DragonFSKY wants to merge 1 commit into
Open
Issue #15514 - Avoid duplicate lifecycle failure logging#15521DragonFSKY wants to merge 1 commit into
DragonFSKY wants to merge 1 commit into
Conversation
Member
|
@DragonFSKY thanks for the PR. You might need to register ECA at Eclipse. Thanks |
Author
|
@olamy Thanks for the reminder. I’ve signed the Eclipse Contributor Agreement and linked my GitHub account. The ECA check is now passing. |
DragonFSKY
force-pushed
the
fix-15514-ssl-load-warning
branch
from
August 2, 2026 00:56
d70e2af to
10cf478
Compare
DragonFSKY
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Removes the legacy failure WARN from
AbstractLifeCycle, which was emitted only when DEBUG logging was enabled and could duplicate startup failure reporting.Exceptions continue to propagate unchanged, the lifecycle still transitions to
FAILED, and listeners receive the same failure cause. The lifecycle tests now assert those behaviors directly.Fixes #15514.